Quote'exact data' is a problem with your scheme, if the verification letter says USA & the order says USa it fails.You should normalize the addy to all lower case, no punctuation, etc.While it should be up to the customer to get this correctly, I suppose this is basically not going to happen. I would personally go with how I would format it normally with capital letters for each section.QuoteBetter is to encrypt the addy using gpg symetric encryption to a truely random 64 byte pw & use that PW as the verification token. Wrap that by encrypting to your own key for your local copy.Decrypting a file is much harder that breaking a hash & the concept is easier for people to understand. Once you destroy the plaintext addy & pw there is no way you can decrypt the addy.If LE intercepts the verification letter they get the token but they already have the address so no harm is done.JofSpadesBasically the PGP/GPG encryption works as long as it's for the end step so it won't mess up the Hash Value of the address. :)QuoteEvery PGP message is different even if the content is the same. Hashing addresses does not create privacy because it is trivial to guess every single address in the world. There are less addresses than people, ie less than 7 billion. You can guess 7 billion hashes in a matter of hours.You cannot be storing addresses in ANY way. Not only is it a bad idea it is against the rules and vendors who do store addresses are rightly banned.I get why you didn't find this idea of any value conceptually at first because of ideological reasons or whatever, but at this point you've crossed into absurdity. I'm not entirely sure of your thought process at this point but let me try and understand it:QuoteHashing addresses does not create privacy because it is trivial to guess every single address in the world.So at face value this would mean you think my plan would be to store the address in itself without any name to it to keep it as simple as possible, because any variation at all in the recipient for the address is obviously going to create a lot more possibilities than seven billion hashes. Now you ignored my point with using a HMAC salt but I assume in this context you're assuming Law Enforcement might hypothetically have the capability of cracking every single password I have which I'll admit might be a possibility if they've been tracking how my brain operates for the last ten years and has the ability to remotely see what I see through my eyes - however if they have that ability your way of doings things will be no more secret than mine. You also ignored the point of JofSpades but I'll give you the benefit of the doubt here and assume you just didn't see it - adding the layer of encrypting the Hash Checksum will make it considerably harder to gain access to even the Hashed Salt Checksum.Also for the final point in what universe does every single Law Enforcement Agency in the world have the name and address to every single person in the entire world, updated on a second to second basis and on top of that it's even trivial for them to brute-force encrypted PGP/GPG encryption and reveal the Hashed Salt Checksum and correctly identify it to an address/person? Considering you even tried arguing this far I don't even get what could hypothetically get you to admit you went too far in your reasoning.QuoteYou cannot be storing addresses in ANY way. Not only is it a bad idea it is against the rules and vendors who do store addresses are rightly banned.How about storing the address on the letters being sent out to customers, which I assume even you have to do?Now to get to the point, the Seller's Guide covers this under the section Client anonymity: http://dkn255hz262ypmii.onion/wiki/index.php?title=Seller%27s_Guide#Client_anonymityQuoteClient anonymityYou and you alone will have your client's shipping address. This information must be destroyed as soon as it is used to label their package. When you click "confirm shipment," the address will be deleted forever and irretrievable.-Never ask your clients for personal information.-Under no circumstance should you save a copy of your client's address.-Publish a Public encryption key in your user description on your settings page so your customers can send you their info encrypted if they wish. -Under no circumstance should you save a copy of your client's address.This is what's being covered and I have no way of retrieving the address without gaining access to the magical database you've mentioned which lists every single person in all multiverses updated continously, along with all encryption methods ever devised until the end of time and beyond. Up until the point this section is changed to include this I'm following the rules by using this method.----------Now I did find another layer to add to this Verification Aspect with the advent of my thread Postal Spam - Where and How? http://dkn255hz262ypmii.onion/index.php?topic=178446.msg1287151Basically any kind of Postal Spam which can be ordered internationally can be used for this purpose. The concept is simply the customer and vendor would have access to the same type of Postal Spam and so the vendor can simply ask the customer to recite any page or characteristic which he will be able to do if he has access to it. Now this won't solve all problems as the customer could still lie about using different addresses and so on but I would qualify it as safer than nothing. I might even consider combining the ideas with sending some kind of Postal Spam in itself with the code hidden on a specific page, or sending an incomplete code with the last two digits sent in a private message through Silk Road. There are obviously a lot of ways to continuously improve this concept which is also what I'm planning on doing.